Method and apparatus for patch panel patch cord documentation and revision

ABSTRACT

A method and apparatus are provided for monitoring and reporting cable connectivity such as patch panel port-level connectivity on a real-time basis. For patch panel systems, the approach is based upon a distributed architecture that may be modularly scalable and may reduce, if not eliminate, the need for a centralized signal processor and complex cabling between patch panels and the centralized signal processor. Each patch panel may determine port level connectivity independently. Polling delays and polling-related overhead processing may be reduced or eliminated by supporting real-time monitoring of port connectivity at the port level. The approach provides improved real-time reporting of patch panel connectivity with reduced cabling complexity, increased reliability, and decreased maintenance costs. In addition, the approach is compatible with (i.e., may communicate with and be controlled by) a multipurpose network management system (NMS). In addition, a compatible revision system is provided.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No.60/624,753, filed Nov. 3, 2004 and entitled “Method and Apparatus forPatch Panel Patch Cord Documentation and Revision.”

BACKGROUND OF THE INVENTION

1. Field of Invention

The present invention pertains to network cable management.

2. Description of Related Art

Communications networks are growing in number and complexity. Monitoringnetwork connections, including the management of patch panelconnections, is an important task in network management. There is adesire for a patch panel management architecture that is reliable andscalable.

SUMMARY OF THE INVENTION

A method and apparatus are provided for monitoring and reporting cableconnectivity such as patch panel port-level connectivity on a real-timebasis. For the patch panel systems example, the approach is based upon adistributed architecture that may be modularly scalable and may reduce,if not eliminate, the need for a centralized signal processor andcomplex cabling between patch panels and the centralized signalprocessor. Each patch panel may determine port-level connectivityindependently. Polling delays and polling-related overhead processingmay be reduced, if not eliminated, by supporting real-time monitoring ofport connectivity at the port level. The approach provides improvedreal-time reporting of patch panel connectivity with reduced cablingcomplexity, increased reliability, and decreased maintenance costs. Inaddition, the approach is compatible with (i.e., may communicate withand be controlled by) a multipurpose network management system (NMS).

A method is disclosed for monitoring cable connections (e.g., a patchpanel patch cord connection) that may include: transmitting a localpatch panel identifier and a local port identifier upon an out-of-bandpatch cord channel; receiving a remote patch panel identifier and aremote port identifier upon the out-of-band patch cord channel;determining a status of the patch cord connection based upon thereceived remote patch panel identifier and the received remote portidentifier; and transmitting a status update message to a networkmanagement system that includes the local patch panel identifier, thelocal port identifier, the remote patch panel identifier, the remoteport identifier, and the status of the patch cord connection.

An apparatus is disclosed for monitoring cable connections (e.g., patchpanel patch cord connections) that may include: a transmitter thattransmits a local patch panel identifier and a local port identifierupon an out-of-band patch cable channel; a receiver that receives aremote patch panel identifier and a remote port identifier upon theout-of-band patch cable channel; a port controller that determines astatus of the patch cord connection based upon the received remote patchpanel identifier and the received remote port identifier and generates aport status update upon determining that a change in the status of thepatch cord connection has occurred; and a patch panel controller thatreceives the port status update and transmits an update to a networkmanagement system that includes the local patch panel identifier, thelocal port identifier, the remote patch panel identifier, the remoteport identifier, and the status of the patch cord connection.

A program product apparatus is disclosed, having a computer-readablemedium with computer program logic recorded thereon for monitoring cableconnections (e.g., a patch panel patch cord connection). The programproduct apparatus may include: a transmitter module that transmits alocal patch panel identifier and a local port identifier upon anout-of-band patch cable channel; a receiver module that receives aremote patch panel identifier and a remote port identifier upon theout-of-band patch cable channel; a port controller module thatdetermines a status of the patch cord connection based upon the receivedremote patch panel identifier and the received remote port identifierand generates a port status update upon determining that a change in thestatus of the patch cord connection has occurred; and a patch panelcontroller module that receives the port status update and transmits anupdate to a network management system that includes the local patchpanel identifier, the local port identifier, the remote patch panelidentifier, the remote port identifier, and the status of the patch cordconnection.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments are described below with reference to the abovedrawings, in which like reference numerals designate like components.

FIG. 1 is a schematic diagram of a single bank of prior art patch panelsthat uses a centralized signal processor to determine connectivitybetween patch panel ports using centralized polling techniques;

FIG. 2 is a schematic diagram of multiple patch panels, each based upona modularly scalable, distributed architecture and capable ofdetermining port level connectivity between patch panels;

FIG. 3 is a schematic diagram depicting messaging exchanged between twopatch panels;

FIG. 4 is a block diagram of an exemplary patch panel depicted in FIGS.2 and 3;

FIG. 5 is a block diagram of an exemplary panel controller module asdepicted in FIG. 4;

FIG. 6 is a block diagram of an exemplary port controller module asdepicted in FIG. 5;

FIG. 7 is an exemplary flow chart of the workflow associated withstartup of an exemplary patch panel;

FIG. 8 is an exemplary flow chart of the workflow associated withoperation of an exemplary patch panel to monitor and report patch panelport level connectivity information;

FIG. 9 is a block diagram of two patch panels for use with a revisionsystem according to one embodiment of the present invention;

FIG. 10 is a perspective diagram of a plug according to one embodimentof the present invention; and

FIG. 11 is a perspective drawing of a portion of a patch panel accordingto one embodiment of the present invention.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The disclosed method and apparatus for monitoring and reporting cableconnectivity may be applied to a variety of network devices. Forexample, as described below, the disclosed method and apparatus may beapplied to monitoring and reporting cable connectivity between patchpanel systems.

FIG. 1 presents an example of a prior art patch panel bank 100 in whichindividual patch panels 102(a-g) have been adapted to support theautomated compilation of patch cord connectivity information. As shownin FIG. 1, each patch panel 102 has a plurality of patch panel ports 104and is connected to a centralized signal processor 106 via a monitoringribbon cable 108(a-g).

Patch cords 112(a-g) used to establish connectivity between two patchpanel ports 104 may include a plurality of network conductors thatsupport network data connections and additional out-of-band conductorsthat support out-of-band signal connections used by patch panel bank 100to monitor the connectivity status of the patch cords. For example, anexemplary RJ-45 style cable terminator may include 8 data conductorstypically associated with an RJ-45 cable terminator and an additionalout-of-band conductor.

Referring again now to FIG. 1, upon insertion of a 9-wire RJ-45 styleconnector, as described above, into an RJ-45 patch panel port 104, theout-of-band connector makes contact with an out-of-band connectorconducting pad (not shown) that is integrated within, or behind, eachRJ-45 patch panel port 104. Each out-of-band conducting pad may beconnected, internally within the patch panel, to one of the multipleconductors within monitoring ribbon cable 108 that connects each patchpanel 102 with centralized signal processor 106. The present inventioncan make use of a connector having nine or more conductors, or it canuse a probe on any type of connector, with the probe making electricalcontact with the patch panel motherboard. Such connectors may be usedwith embodiments of the present invention, including the embodiment ofFIG. 2.

In patch panel bank 100, to determine connectivity between individualpatch panel ports 104 established by patch cords 112, centralized signalprocessor 106 polls each port 104 on each patch panel 102 via therespective monitoring ribbon cables 108. For example, centralized signalprocessor 106 may sequentially place an electrical signal, such as a DCvoltage, upon a selected conductor within a selected monitoring ribboncable 108 and detect whether the signal is received upon anothermonitoring ribbon cable 108 conductor associated with the same patchpanel or another patch panel connected to centralized signal processor106. If a signal is detected upon a monitoring ribbon cable 108conductor in response to a signal being placed upon another conductorwithin the same or a different monitoring ribbon cable 108, centralizedsignal processor 106 may determine that the two patch panel portsassociated with the respective ribbon cable conductors are connected.Centralized signal processor 106 may generate and transmit a message toa Network Management System (NMS) via a management network connection110 to report the determined port level connectivity. If no signal isdetected upon a monitoring ribbon cable 108 conductor in response to asignal being placed upon a conductor within the same or differentmonitoring ribbon cable 108 associated with a specific patch panel port,centralized signal processor 106 determines that the patch panel portupon which the signal is placed is not in use.

Although a monitored patch panel bank 100, as described above withrespect to FIG. 1, is capable of providing a network management systemwith patch panel connectivity information, such monitored banks of patchpanels have significant drawbacks. The approach is not modularlyscalable in that the centralized signal processor 106 is limited in thenumber of physical patch panels to which it can connect and, therefore,is limited in the number of patch panel connections that can bemonitored. Although additional centralized signal processors may beobtained to support different banks of patch panels, patch cordsconnected between patch panels supported by different centralized signalprocessors cannot be monitored. Further, the monitored patch panel bank100 based approach makes the centralized signal processor a single pointof failure with respect to monitoring the bank of patch panels. Loss ofa single centralized signal processor 106 (e.g., due to a loss of power,loss of a network connection, or due to an internal centralized signalprocessor failure) results in a loss of patch panel monitoringcapability for the entire bank of patch panels. Further, the need toconnect to a centralized signal processor panel places restraints uponthe placement of patch panels and increases cable complexity, thusdecreasing reliability and increasing maintenance costs. Still further,increases in the number of panels supported by a single centralizedsignal processor increases the polling requirements placed upon thecentralized signal processor, thus increasing polling cycle time (i.e.,the time required to poll all ports on all patch panels) and decreasingresponsiveness of the system to changes in patch panel patch cordconnectivity.

In view of the above, a patch panel capable of monitoring and reportingpatch panel port-level connectivity that is based upon a modularlyscalable, distributed architecture is desirable. Such an approach wouldpreferably reduce, if not eliminate, the need for a centralized signalprocessor by allowing each patch panel to determine port levelconnectivity independently. Further, such an approach would preferablyreduce, if not eliminate, polling delays and polling-related overheadprocessing by supporting real-time monitoring of port connectivity atthe port level. In addition, such an approach would provide real-timereporting of patch panel connectivity with reduced cabling complexity,increased reliability and decreased maintenance costs.

FIG. 2 is a schematic diagram of seven exemplary modular, intelligentpatch panels 202(a-g). Each patch panel 202 is based upon a modularlyscalable, distributed architecture. As shown in FIG. 2, each patch panel202 may include a pair of network connection ports 220 that allow therespective patch panels to be interconnected in a daisy-chainconfiguration to a network connection 210 using daisy-chain networkcables 208 (e.g., relatively short spans of 4-pair network cableterminated in conventional RJ-45 terminators). Network connection 210may provide network connectivity to each patch panel in the daisy-chainand may thereby provide each patch panel in the daisy-chain withconnectivity to a remote Network Management System (NMS). Further, eachpatch panel 202 may include a pair of power sharing ports 218 that allowthe patch panels to be interconnected in a daisy-chain configuration toa single power supply 222 using daisy-chain power cables 216 (e.g.,relatively short spans of DC or AC electrical power cabling withappropriate connectors).

Each patch panel 202 is capable of monitoring and reporting patch panelport level connections formed by patch cords manually connected betweenports on one or more patch panel devices without support from acentralized signal processor (e.g., as described with respect to FIG. 1block 106). Therefore, the patch panel may reduce or eliminate the needfor status-monitoring ribbon cables (as described with respect to FIG.1). The ability to daisy-chain power to multiple patch panels from asingle power supply 222 may reduce or eliminate the need for independentpower supplies to each individual patch panel and further reduces thevolume of power-related cables. The ability to daisy-chain networkconnectivity to multiple patch panels from a network connection 210 mayreduce or eliminate the need for independent network cables for eachindividual patch panel and further reduces the volume of network-relatedcables.

The patch panel architecture allows network patch panel capabilities tobe scaled in any manner by the introduction of any number of patch paneldevices. The patch panel architecture allows patch cord connectivitybetween any two patch panel ports to be determined based uponout-of-band communication between the respective connected ports over anout-of-band patch cord connection. The patch panel may reduce oreliminate the need for a common centralized signal processor todetermine connectivity between patch panel ports. Further, eliminationof the need for a centralized signal processor may remove a single pointof failure with respect to the ability to monitor a set of patch panelsand may remove or eliminate multiple other potential points of failurevia simplified cabling. Further, unlike the polling approach describedabove with respect to FIG. 1, the patch panel architecture supports themonitoring and the reporting of changes in patch panel port-levelconnectivity on a real-time basis, regardless of the number of patchpanels included in the network. Response time does not increase with thenumber of patch panels added to a network, as is the case with systemsthat rely upon a centralized signal processor to sequentially scan eachport on each of the respective patch panels that the centralized signalprocessor supports. The patch panel architecture according to someembodiments of the present invention supports patch panel monitoringthat may be modularly scaled to support any size network, providesreal-time monitoring with reduced delay, and employs a simplifiedinter-patch-panel cabling scheme that increases reliability and reducesmaintenance costs.

FIG. 3 is a schematic diagram depicting an exchange of out-of-bandmessages between a patch panel 302(a) labeled “patch panel X” and apatch panel 302(b) labeled “patch panel Z.” As described in greaterdetail below, each patch panel port may repeatedly broadcast over theout-of-band channel a port message identifying the patch panel and portgenerating the message. For example, as shown in FIG. 3, patch panelport 304(a) associated with panel X may generate an outbound message“patch panel X/Port 21” to indicate that patch panel port 304(a) is thetwenty-first port on patch panel X. Further, as shown in FIG. 3, port304(b) associated with patch panel Z may generate an outbound message“patch panel Z/Port 17” to indicate that patch panel port 304(b) is theseventeenth port on patch panel Z.

Each patch panel port may repeatedly broadcast an outbound message andlisten for receipt of an outbound message generated from another patchpanel port. Until a patch cord that supports the out-of-bandcommunication channel is connected between two patch panel ports,neither port will receive an out-of-band message. However, uponconnection of two patch panel ports with a patch cord that supports anout-of-band communication channel (e.g., a patch cord with a 9^(th)wire) each patch panel port may receive the outbound message broadcastby the patch panel port with which it has established connectivity. Thepatch panel port controller associated with each of the respective portsmay then generate, in real time, an update message to its respectivepatch panel controller. Upon receipt of an update message from a portcontroller, each respective patch panel controller may generate andtransmit an update message over a network connection to a remote NMSthat is configured to organize and present the received physicaltopology information in a manner useful to an end user.

FIG. 4 is a block level diagram of an exemplary patch panelconfiguration. As shown in FIG. 4, patch panel 400 includes a panelcontroller module 402 that communicates with a plurality of portcontroller modules 404. Further, the patch panel controller module 402may support communication with another patch panel and/or a networkmanagement system via daisy-chain network connection ports 420(a) and420(b), as described above. In addition, the patch panel may receiveelectrical power from a power supply or another patch panel and maytransfer power to another patch panel via daisy-chain power connectionports 418(a) and 418(b), as described above.

FIG. 5 is a block diagram of an exemplary patch panel controller module502. As shown in FIG. 5, panel controller module 502 may include a panelprocessor module 510 in communication with a data storage module 508, anetwork interface module 506 and a plurality of port controller modules504.

Panel processor module 510 may communicate with each of the respectiveport controller modules 504 to receive port status updates. Upon receiptof an update message from a port controller module 504, panel processormodule 510 may update status information stored within data storagemodule 508, generate an SNMP compliant update message that includesconnection related information received from the port controller module,and transmit the generated SNMP compliant update message to a remotenetwork-connected NMS via network interface module 506. A ninth wireconnection 509 or other probe connection is connected to the patch panelout-of-band channel physical interface and the port controller module504. The in-band communications, carried in the embodiment of FIG. 5through eight conductors 511, proceed through the patch panel withoutmodification.

Panel processor module 510 may receive and process SNMP messages fromthe remote network connected NMS via network interface module 506. TheSNMP message may contain updated configuration parameters for use incontrolling the panel controller module 502 and/or one or more of portcontroller modules 504. Upon receipt of an update message from a remotenetwork-connected NMS, panel processor module 510 may update statusinformation stored within data storage module 508 and generate/transmitan internal update message to each of the respective port controllermodules 504.

Although not indicated in FIG. 5, panel processor module 510 may includeadditional functionality or modules for use in controlling the behaviorand operation of the patch panel. Such additional modules may storeand/or update within data storage module 508 managed objects associatedwith the additional functions performed. Preferably, such objects arestored in a structure and format compatible with a defined SNMPManagement Information Base (MIB) to facilitate SNMP-based reporting(e.g., via an SNMP get-response message and/or via an SNMP event trapmessage, etc.) of the stored values from the panel processor module 510to the NMS and/or to support updates from the NMS to patch panelcontroller module 502 via SNMP based messages (e.g., via the SNMP setcommand). An additional function that may be included in panel processormodule 510 supports the receipt and processing of command, control andreporting instructions from the NMS via protocols other than SNMP.

Different panel controller module 502 configurations may include a panelprocessor module 510 with capabilities that range from nominal functionsto sophisticated monitoring and control functions. As such, thehardware/software modules required to implement panel controller module502 may range from relatively simple modules with limited storage andprocessing capabilities to relatively complex modules with significantstorage and processing capabilities.

FIG. 6 is a block diagram of an exemplary port controller module 604. Asshown in FIG. 6, port controller module 604 may include a port processormodule 606 in communication with a data storage module 612. Portprocessor module 606 communicates with an out-of-band channel physicalinterface 610.

Port processor module 606 may communicate with the patch panelcontroller module to send port update messages to the panel controllermodule and to receive configuration/control parameter updates from thepanel controller module. Upon receipt of an update message from thepanel controller module, port processor module 606 may update statusinformation stored within data storage module 612. Port processor module606 may use parameters received from the patch panel controller moduleand stored in data storage module 612 to control operation of portcontroller module 604 and to control events reported via update messagesto the panel controller module.

In one exemplary port controller module, port processor module 606 mayretrieve from data storage module 612 a local patch panel identifier, alocal port identifier, and a local port connection status associatedwith the current, or local, port controller module (e.g., patchpanel/port information related to the current, or local, patch panelport) and may provide the retrieved information to out-of-band channelphysical interface 610, generating an outbound port message thatincludes the retrieved local patch panel identifier and local portidentifier information. The port processor module 606 may proceed totransmit the message upon the out-of-band channel via a transmitter,which in one embodiment is operated by out-of-band channel physicalinterface 610. Further, the port processor module 606 may receive aninbound message from a remote port that includes a remote patch panelidentifier and remote port identifier information, via a receiver whichmay be operated by out-of-band channel physical interface 610.

In an exemplary configuration in which out-of-band channel physicalinterface 610 supports a single out-of-band conductor, the portprocessor module 606 may repeatedly alternate between transmitting anoutbound port message and checking to see if an outbound message from aremote port may be received. In another exemplary configuration in whichthe out-of-band channel physical interface 610 supports two separateout-of-band conductors, the port processor module 606 may simultaneouslytransmit an out-of-band outbound port message and check for/receive anout-of-band message from a remote port, simultaneously.

The terms “remote port” and “local port” are relative terms. Forexample, from the perspective of a patch panel port controller, the term“remote port” may be used to refer to any port other than the “localport” supported by that patch panel port controller. Given that a patchpanel supports multiple ports, a “remote port” may be a port on thesame, or local, patch panel as a “local port” or the “remote port” maybe a port on another, or remote, patch panel. A remote port and a localport behave, and are, exactly the same except that each has a relativeposition with respect to the other. For example, each port, based uponthe perspective of that port, transmits an out-of-band outbound portmessage that includes a local patch panel identifier and a local portidentifier. Further, each port, based upon the perspective of that port,receives a remote patch panel identifier and a remote port identifierwithin a received message.

Upon determining, based upon the monitored out-of-band messages, that achange in port level connectivity has occurred, port processor module606 may store the updated status information in data storage module 612and send an update message to the panel controller module, as describedabove with respect to FIG. 5.

As described above, different port controller module 604 configurationsmay include a port processor module 606 with capabilities that rangefrom nominal functions to sophisticated functions. As such, thehardware/software modules required to implement port controller module604 may range from relatively simple modules with relatively slightstorage and processing capabilities to relatively complex modules withrelatively significant storage and processing capabilities.

FIG. 7 is a flow chart of an exemplary workflow associated with thestartup of an exemplary patch panel device. As shown in FIG. 7, uponpowering up, at step S702, of a patch panel device, the patch panelpanel controller may send, at step S704, a configuration request to aremote NMS. Upon receipt, at step S706, by the NMS of the configurationrequest, the NMS may retrieve, from a configuration controlled storagerepository, configuration parameters for the patch panel device fromwhich the configuration request was received and send the retrievedconfiguration parameters to the patch panel panel controller. Uponreceipt, at step S708, of the requested configuration parameters, thepatch panel panel controller may store the received parameters and send,at step S710, all or a portion of the received configuration parametersto each of the respective patch panel port controllers associated witheach of the respective patch panel ports to which all or portions of therespective configuration parameters apply. Upon receipt, at step S712,of configuration data from the panel controller, each port controllermay store the configuration parameters and may initiate, at step 714,port connectivity monitoring in accordance with the received controlparameters, as described above.

FIG. 8 is a flow chart of an exemplary workflow associated withmonitoring patch panel port-level connectivity based the monitoring ofcommunications upon an out-of-band communication channel, as describedabove. As shown in FIG. 8, upon initiation of patch cord connectivitymonitoring, a patch panel port controller may transmit, at step S802, anoutbound message upon the out-of-band channel associated with themonitored port. Such an outbound message may contain patch panel/portinformation associated with the monitored patch panel port.

Next, the port controller may check, at step S804, to determine whetheran out-of-band message from another patch panel port controller isavailable for receipt. If the port controller determines, at step S806,that an out-of-band message is not available for receipt, the portcontroller checks, at step S808, the currently stored port status. Ifthe port controller determines that the stored connection statusindicates that the port is not connected, the process flow proceeds toS802 to again transmit an out-of-band channel outbound messagecontaining patch panel/port information associated with the monitoredpatch panel port. If the port controller determines, at step S808, thatthe stored connection status indicates that the port status is“connected,” the port controller may update, at step S810, a port-leveldata store to reflect the new port status as “disconnected” and maygenerate and send to the patch panel controller a message notifying thepanel controller of the disconnect. Upon receipt of the message from theport controller containing a new port status, the panel controller maystore the port status information in a panel level information store andgenerate/transmit a status update to the NMS via the network. Theprocess flow may then proceed to step S802.

If the port controller determines, at step S806, that an out-of-bandmessage is available for receipt, the port controller receives, at stepS812, the out-of-band message. If the port controller determines, atstep S814, that the port status is “connected” and that the receivedpatch panel/port information matches previously stored patch panel/portinformation, no update to the panel controller is generated andprocessing may proceed to step S802.

However, if the port controller determines, at step S814, that thestored port status is “disconnected” and/or that the received patchpanel/port information does not match previously stored patch panel/portinformation, the port controller may conclude that a change in portconnectivity status has occurred. Therefore, at step S816, the portcontroller may update the port level data store to reflect a port statusof “connected” and may send a message to the panel controller containingthe new port status and the newly received patch panel/port connectioninformation. The panel controller receives, at step S818, the updatemessage and in response may update the panel-level information store toreflect the received connection status and port connectivity informationand may generate and transmit an update message via the network to theNMS. The process flow may then proceed to step S802.

FIG. 9 shows one embodiment of the present invention which is used forcross-connect systems wherein all patch cords are connected betweenpatch panels in group 1 (group 1 ports) and patch panels in group 2(group 2 ports). In this embodiment, there is a MAC chip associated witheach port of each patch panel. Each system transmission on a 9^(th) wireis from a group 1 port to a group 2 port. Each group 1 port continuouslysends its MAC ID over its 9^(th) wire. If such a signal is received at agroup 2 port, the IDs of both the group 1 port and the group 2 port aresent to the NMS by the group 2 port. When receipt by the NMS isacknowledged, the group 2 port stops sending the message. If a group 2port stops receiving the MAC ID signal from the group 1 port, ittransmits its ID continuously to the NMS until receipt is acknowledgedby the NMS. The NMS is therefore continuously updated. Thisdocumentation system does not require a data storage module in eachpatch panel. A central revision system which is a subsystem of the NMSalso controls an LED associated with each port. The transmissions toeach patch panel to control the LED's are on the same Ethernet systemused for the documentation system.

Turning again to FIG. 9, a revision system is illustrated using a firstpatch panel 900 and a second patch panel 902 according to the presentinvention. A port 904 on the first patch panel 900 is connected upstreamto a network switch 906. The revision system is a sub-system in thenetwork management system (NMS). The revision system can guide theremoval or the addition of a patch cord. Each patch panel port isprovided with an LED.

To guide the removal of a patch cord, the revision system causes a firstLED 908 of the first port 904 and a second LED 910 of a second port 912,to which the patch cord 914 is attached, to flash. In the embodiment ofFIG. 9, the patch cord 914 is a nine-wire patch cord. The revisionsystem next causes MAC ID's of the first port 904 and the second port912 to be sequentially and continuously sent to the revision system byport 912. A reviser unplugs the patch cord 914 from the second port 912,which is associated with the flashing LED 910. The revision system nextcauses only the MAC ID of the second port 912 to be continuously sent tothe revision system until it receives the message. The revision systemthen turns off the LED 910 of the second port 912 and, after a timedelay, also turns off the LED 908 of the first port 904.

To guide the addition of a patch cord, the revision system lights boththe first LED 908 and the second LED 910. When the patch cord connectingthe first and second ports 904 and 912 is installed, both ID's are sentsequentially and continuously by port 912 to the revision system untilthe revision system receives the message and turns off both LED's.

FIGS. 10 and 11 illustrate a plug and a number of jacks as shown by thecircle “A” of FIG. 9. FIG. 10 shows a plug 1000 having a contact 1002 atthe top. The contact 1002 is electrically connected to the ninth wire ofthe plug's patch cord, and is designed to mate with ninth-wirereceptacles 1100 as shown in FIG. 11 when the plug is inserted into ajack 1102. Also shown in FIG. 11 are LED's 1104 associated with each ofthe jacks. Plugs and jacks as shown in FIGS. 10 and 11 may be used inother embodiments of the present invention.

It will be appreciated that the exemplary embodiments described aboveand illustrated in the drawings represent only a few of the many ways ofimplementing patch panels according to the present invention for use inmanaging network patch panel connections. The present invention is notlimited to use within any specific network cable infrastructureconfiguration disclosed herein, but may be applied to any deployednetwork infrastructure that may benefit from the use of patch panels.Further, the automated cable management capability described may beintegrated within any network connected device, including but notlimited to a switch, a router, a computer, a server, a network connecteddata repository, an end-user device such as a printer, a workstation,and a hand-held computing device.

The patch panel may be implemented in any number of hardware andsoftware modules and is not limited to any specific hardware/softwaremodule architecture. Each patch panel module may be implemented in anynumber of ways and is not limited in implementation to execute processflows precisely as described above. The patch panel patch cordconnection monitoring process described above and illustrated in theflow charts and diagrams may be modified in any manner that accomplishesthe functions described herein.

It is to be understood that various functions of the patch panel patchcord management methods and apparatus may be distributed in any manneramong any quantity (e.g., one or more) of hardware and/or softwaremodules or units, computer or processing systems or circuitry.

A patch panel that supports the patch cord connection monitoring processmay support patching of any type of network cabling, including but notlimited to copper and/or optical fiber cabling. Port connections on theface plate of a patch panel and/or a patch panel network connection portmay support any type of cable and cable connector, including but notlimited to RJ-45 based connectors and optical fiber connectors. Portconnections on the rear plate of a patch panel may support any type ofcable and cable connector, including but not limited to punch-downports, RJ-45 ports, optical fiber connections, etc.

Patch panel network connectivity is not limited to the use ofdaisy-chain network connectivity between patch panel devices. Individualpatch panel devices may connect to a network through any type of networkconnection, either directly or via an indirect, or shared, connection.

Patch panel power connectivity is not limited to the use of adaisy-chain power connection between patch panel devices. Individualpatch panel devices may connect directly to a dedicated power source ora shared power source, either directly or via an indirect connection.

Network Management System processes associated with the patch panelpatch cord connection monitoring processes may be integrated within astand-alone system or may execute separately and be coupled to anynumber of devices, workstation computers, server computers or datastorage devices via any communication medium (e.g., network, modem,direct connection, etc.). The Network Management System processesassociated with the patch panel patch cord connection monitoring processcan be implemented by any quantity of devices and/or any quantity ofpersonal or other type of computers or processing systems (e.g.,IBM-compatible, Apple, Macintosh, laptop, palm pilot, microprocessor,etc.). The computer system may include any commercially availableoperating system (e.g., Windows, OS/2, Unix, Linux, DOS, etc.), anycommercially available and/or custom software (e.g., communicationsoftware, traffic analysis software, etc.) and any types of input/outputdevices (e.g., keyboard, mouse, probes, I/O port, etc.).

The patch panel and Network Management System software associated withthe patch panel patch cord connection monitoring process may beimplemented in any desired computer language, and could be developed byone of ordinary skill in the computer and/or programming arts based onthe functional description contained herein and the flow chartsillustrated in the drawings. For example, in one exemplary embodimentthe patch panel patch cord connection monitoring process may be writtenusing the C++ programming language, however, the present invention isnot limited to being implemented in any specific programming language.The various modules and data sets may be stored in any quantity or typesof file, data or database structures. Moreover, the software associatedwith the patch panel patch cord connection monitoring process may bedistributed via any suitable medium (e.g., stored on devices such asCD-ROM and diskette, downloaded from the Internet or other network(e.g., via packets and/or carrier signals), downloaded from a bulletinboard (e.g., via carrier signals), or other conventional distributionmechanisms).

The format and structure of internal information structures used to holdintermediate information in support of the patch panel patch cordconnection monitoring process, and network cable management with respectto devices other than the patch panel, may include any and allstructures and fields and are not limited to files, arrays, matrices,status and control booleans/variables.

The Network Management System used to support the patch panel patch cordconnection monitoring process software may be installed and executed ona computer system in any conventional or other manner (e.g., an installprogram, copying files, entering an execute command, etc.). Thefunctions associated with the Network Management System may be performedon any quantity of computers or other processing systems. Further, thespecific functions may be assigned to one or more of the computersystems in any desired fashion.

The patch panel patch cord connection monitoring process may accommodateany quantity and any type of data set files and/or databases or otherstructures containing stored data sets, measured data sets and/orresidual data sets in any desired format (e.g., ASCII, plain text, anyword processor or other application format, etc.).

Patch panel patch cord connection monitoring process output may bepresented to the user (e.g., via the Network Management System) in anymanner using alphanumeric and/or visual presentation formats. Patchpanel connection data may be presented in either alphanumeric or visualform and can be processed by the NMS in any manner and/or using anynumber of threshold values and/or rule sets.

Further, any references herein to software performing various functionsgenerally refer to computer systems or processors performing thosefunctions under software control. The computer system may alternativelybe implemented by hardware or other processing circuitry. The variousfunctions of the patch panel patch cord connection monitoring processmay be distributed in any manner among any quantity (e.g., one or more)of hardware and/or software modules or units, computers or processingsystems or circuitry. The computer or processing systems may be disposedlocally or remotely of each other and communicate via any suitablecommunication medium (e.g., LAN, WAN, Intranet, Internet, hardwire,modem connection, wireless, etc.). The software and/or processesdescribed above and illustrated in the flow charts and diagrams may bemodified in any manner that accomplishes the functions described herein.

From the foregoing description it will be appreciated that anintelligent patch panel and method of managing network patch panelconnections using a patch panel architecture are disclosed that arecapable of accurately assessing, and reporting in real-time, deployedpatch panel patch cord connectivity information.

While a patch panel and method of managing network patch panelconnections using a patch panel architecture are disclosed, anymodifications, variations and changes within the skill of one ofordinary skill in the art fall within the scope of the presentinvention. Although specific terms are employed herein, they are used intheir ordinary and accustomed manner only, unless expressly defineddifferently herein, and not for purposes of limitation.

1. A method for monitoring a cable connection, comprising: transmittinga local device identifier and a local port identifier associated with alocal device; receiving a remote device identifier and a remote portidentifier associated with a remote device; determining a status of thecable connection based upon the received remote device identifier andthe received remote port identifier; and transmitting a status updatemessage to a network management system that includes the local deviceidentifier, the local port identifier, the remote device identifier, theremote port identifier, and the status of the cable connection.
 2. Themethod of claim 1, wherein the local device and the remote device arepatch panels.
 3. The method of claim 2, further comprising comparing thereceived remote device identifier with a stored previously receivedremote device identifier and a stored previously received remote portidentifier and notifying a device controller upon determining that achange in the status of the cable connection has occurred.
 4. The methodof claim 2 wherein transmitting a status update message to a networkmanagement system comprises transmitting said status update message viaa daisy-chain network connection connecting a plurality of devices tothe network.
 5. The method of claim 2 further comprising storing aplurality of managed data items in a data store within at least one ofsaid local and remote devices in accordance with a defined SNMPmanagement information base.
 6. An apparatus for monitoring a cableconnection between two patch panels, comprising: a local patch panelhaving a transmitter that transmits a local patch panel identifier and alocal port identifier associated with a port of the local patch paneland also having a receiver that receives a remote patch panel identifierand a remote port identifier associated with a port of a remote patchpanel; a port controller that determines a status of the cableconnection between the local patch panel and the remote patch panelbased upon the received remote patch panel identifier and the receivedremote port identifier and generates a port status update upondetermining that a change in the status of the cable connection hasoccurred; and a device controller that receives the port status updateand transmits an update to a network management system that includes thelocal patch panel identifier, the local port identifier, the remotepatch panel identifier, the remote port identifier, and the status ofthe cable connection.
 7. The apparatus of claim 7, wherein thetransmitter and the receiver of the local patch panel respectivelytransmit and receive signals upon an out-of-band channel.
 8. Theapparatus of claim 7 wherein said cable connection between said twopatch panels comprises a cable completing an eight-conductor electricalconnection and wherein said out-of-band channel comprises at least oneextra conductor of said cable.
 9. The apparatus of claim 6 wherein saidport controller further comprises a comparison module that compares thereceived remote patch panel identifier and the received remote portidentifier with a previously stored received remote patch panelidentifier and a previously stored received remote port identifier. 10.The apparatus of claim 6 wherein said local patch panel furthercomprises a network module that communicates with the network managementsystem.
 11. The apparatus of claim 6 wherein said local patch panel andsaid remote patch panel are connected to each other in a daisy chainconfiguration via daisy chain network cables.
 12. The apparatus of claim6 wherein said local patch panel and said remote patch panel have patchpanel power modules, said patch panel power modules being connected toeach other and being further connected to a shared power source via adaisy chain power connection.
 13. The apparatus of claim 6 wherein eachof said local patch panel and said remote patch panel further comprisesa data-store module that stores a plurality of managed data items withina data store within each of the patch panels.
 14. An apparatus formonitoring a cable connection between two patch panels comprising: afirst patch panel comprising a plurality of first patch panel ports,each of said first patch panel ports comprising an in-band communicationchannel connector and an out-of-band communication channel contact, saidfirst patch panel further comprising a first port controller moduleconnected to said out-of-band communication channel contact of at leastone of said first patch panel ports, said first patch panel furthercomprising a first patch panel controller module in communication withsaid first port controller module; and a second patch panel comprising aplurality of second patch panel ports, each of said second patch panelports comprising an in-band communication channel connector and anout-of-band communication channel contact, said second patch panelfurther comprising a second port controller module connected to saidout-of-band communication channel contact of at least one of said secondpatch panel ports, said second patch panel further comprising a secondpatch panel controller module in communication with said second portcontroller module; wherein said first port controller module is adaptedto communicate via said out-of-band communication channel contact withsaid second port controller module.
 15. The apparatus of claim 14wherein said first port controller module is under the control of saidfirst patch panel controller module and said second port controllermodule is under the control of said second patch panel controllermodule.
 16. The apparatus of claim 14 further comprising at least oneindicator light associated with each of said first patch panel ports andsaid second patch panel ports.
 17. The apparatus of claim 14 whereinsaid first patch panel further comprises primary and secondary firstpatch panel network connector ports and said second patch panel furthercomprises primary and secondary second patch panel network connectorports; wherein the primary first patch panel network connector port isconnected to one of said second patch panel network connector ports, andthe secondary first patch panel network connector port is connected to anetwork management system.
 18. The apparatus of claim 14 wherein saidfirst patch panel controller module comprises a network interfacemodule, a panel processor module, and a data storage module.
 19. Theapparatus of claim 14 wherein said in-band communication channelconnectors are electrical connectors.
 20. The apparatus of claim 14wherein said in-band communication channel connectors are opticalconnectors.